2. General information. 2.1 Menus. Without exception throughout Acmenav, all menus are exited by using the hot key combination Psion X, or selecting the exit option from the special section of that menu. 2.2 Dialogue boxes. There are many occasions in Acmenav when a whole series of dialogue boxes are used to enter data. Almost without exception, a dialogue box can be cancelled and the previous one viewed and edited by pressing . There are a few exceptions to this rule which are discussed in the relevant sections of this manual. 2.3 Temporary files. There are a number of occasions when Acmenav needs to create a file, either because a file that is required has been deleted, or because it hasn't yet been created. All such files will always initially be created in the \dat\Acmenav sub-directory on the ramdisk. You will be informed when this happens by a small message apperaing in the bottom left hand corner of the display. Once these "temporary" files have been created, and provided they are stored in a sub-directory called \dat\Acmenav, they can be copied to either disk a or disk b (alernatively they can be kept in the ramdisk). 2.4 Location of files. It was stated earlier on in this manual that you can move all files with the extension .opo and .odb .fpl and .log to any storage device. When Acmenav needs to gain access to a file or module, it always searches for it in the order ramdisk, device a, and then device b. The first file that it comes across it will use. This does of course mean that you can have several logbook files, or multiple database files, but do remember the search sequence for accessing them! 2.4 Help. The only source of help, apart from dropping me a line via CIS is this manual. Pressing the help key will achieve nothing in this department. I really am of the opinion that Acmenav is that easy to use! 2.5 Type 0 application. Acmenav is a type 0 application; no file names will appear under its icon in the system screen. 2.6 Printer support. Acmenav v1.0 contains no printer support; it is designed to be used in flight. It is likely that the next major update (versin 3) will contain at least some printer support. 2.7 Interfacing with other applications. Acmenav does not interface with any other Series 3 applications; you cannot use the "bring" option in other applications to export data from Acmenav and neither can you import data from other applcations into Acmenav. 2.8 Latitude and longitude. There are three common ways of expressing latitude and longitude: as degrees, minutes and seconds, as sexagesimal degrees (with the minutes and seconds combined to form the decimal part of the degree figure) and as degrees, minutes and decimal seconds (the seconds form the decimal part of the minutes). Acmenav supports the last two methods in that on all the occasions that a position has to be entered, a common dialogue box is used that allows inputs by sexagesimal degrees, or degrees minutes and decimal seconds. It is perfectly acceptable to mix the two types, one for latitude and another for longitude although I can't forsee why someone should ever need to do this. All points of latitude south of the equator and points of longitude east of the prime meridian should be entered as negative values. If you enter a negative figure for degrees, the minutes figure, if entered, should also be negative. 2.9 Magnetic variation. Acmenav does not contain details of magnetic variation. One of the reasons for this is to force users to at least glance at a chart whilst planning flights to extract the necessary information. It is hoped that pilots will take this oppotunity to brief the route properly. Although Acmenav doesn't contain magnetic variation data initself, there are times when it is needed by the system. On these occasions westerly variation should be enetered as a positive value and easterly variation as a negative value. 2.10 Statute miles. Throughout Acmenav, standard unit abbreviations have been used wherever possible. The exception to this rule is the abbreviation "sm" which is used for statute miles.